home *** CD-ROM | disk | FTP | other *** search
- Path: nov-mirsev.cicese.mx!not-for-mail
- From: mirsev@cicese.mx (Serguei Miridonov)
- Newsgroups: comp.dcom.modems
- Subject: Re: Need help with USR Init String
- Date: 29 Jan 1996 18:53:35 -0800
- Organization: CICESE, Ensenada B.C., Mexico
- Message-ID: <4ek17f$vco@nov-mirsev.cicese.mx>
- References: <4dv6ub$lcq@ccnet2.ccnet.com> <eric-2601960054250001@sobt.accessorl.net>
- NNTP-Posting-Host: nov-mirsev.cicese.mx
- X-Newsreader: TIN [version 1.2 PL2]
-
- On Fri, 26 Jan 1996 00:54:25 -0500 Eric Shaw (eric@accessorl.net) wrote:
- > In article <4dv6ub$lcq@ccnet2.ccnet.com>, fearless@ccnet.com (fjc) wrote:
-
- > >I've got a new USR Sportster Vi modem (with DSVD) that I'm having a hard time
- > >connecting to my ISP with. I think the problem is mine because I connect fine
- > >with my Cardinal 288i MVP modem ( I have them both connected to my PC).
- > >Trouble is my Cardinal connection is very shaky; I get dropped quickly and
- > >often.
-
- > The most common reason for getting dropped when netsurfing seems to be
- > hardware DTR hangup - if your computer is busy swapping, it can't always
-
- Why do you think that computer drops DTR while swapping? DTR is set by
- communication software and usually never dropped until communication
- program exits. Instead, RTS is dropped in some programs when it is
- writing on a disk. But RTS toggle can not cause modem hangup. It just
- stops transferring data from modem to computer if hardware handshake
- is ON (as it should be to avoid com port overruns).
-
- > keep the DTR line to the modem raised, so try the cardinal with this
- > feature off (AT&D0) and you might stop getting dropped.
-
- This command works in Sportster Vi DSVD as well. But I set it AT&D3 to
- reset the modem after the session. It could be good in Linux because
- I use many different communication programs and may be not good idea for
- MSDOS or Windows...
-
- > >The USR connection on the other hand seems much more stable IF I get
- > >connected.
-
- > USR's don't always connect v.34 with other brand modems, ESPECIALLY the
- > Vi. When the Vi does connect with v.34, it is almost NEVER with v.42
- > error correction.
-
- It is absolutely wrong. I don't know what are you talking about, but my
- Sportster Vi with DSVD always connects at v.34 with ARQ to Couriers at
- USR BBS and Hayes Accura (if the v.34 is not disabled explicitly). I've
- never seen CONNECT XXXXX/NONE. Well, I had some problems connecting to
- Hayes (see below).
-
- > Don't disable v.34 directly though, or you'll connect
- > v.32bis (14.4K) Instead, disable v.8. On most USR 28.8's, this is
- > S54.7=1. Then you will connect with v.FC (assuming the modem at the other
- > end supports both).
-
- It seems to be true for some types of modems. At least, I'm setting
- S54=192 (disables v.8 which in turn disables v.34) before connection
- with Hayes Accura v.34&v.FC. As a result, I have much less blers and
- higher average connection rate at v.FC than at v.34. From the other
- hand, I have no problems with connections to Couriers at USR BBS at
- v.34.
-
- I don't remember exact init string for my modem because I put it in NVRAM
- and initialize it with ATZ. Try AT&F1&K3&D3S56=0 before dialing out and if it
- works for you, then put it in NVRAM with AT&W. Note S56=0 ! I don't know
- why but in the original &F1 profile it is set to 128 which disables v.FC.
-
- If you have problems with some modems at v.34, try S54=192 or S54.7=1. It
- will connect you at v.FC if remote modem supports it.
-
- Serguei Miridonov.
-
-